From 416d132a72798d9f8af58ad73747cd4f0c935855 Mon Sep 17 00:00:00 2001 From: Benjamin Otte Date: Wed, 11 Aug 2010 05:12:49 +0200 Subject: [PATCH] docs: Some style fixes to the migration guide Most importantly, I decided to not capitalize "cairo". --- docs/reference/gtk/migrating-2to3.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/gtk/migrating-2to3.xml b/docs/reference/gtk/migrating-2to3.xml index 1652177cf8..389a578c0d 100644 --- a/docs/reference/gtk/migrating-2to3.xml +++ b/docs/reference/gtk/migrating-2to3.xml @@ -6,7 +6,7 @@ Migrating from GTK+ 2.x to GTK+ 3 - GTK+ 3 is a major new version of GTK+, which breaks both API and ABI + GTK+ 3 is a major new version of GTK+ that breaks both API and ABI compared to GTK+ 2.x, which has remained API- and ABI-stable for a long time. Thankfully, most of the changes are not hard to adapt to and there are a number of steps that you can take to prepare your @@ -96,7 +96,7 @@
- Use accessor functions instead direct access + Use accessor functions instead of direct access GTK+ 3 removes many implementation details and struct members from its public headers. @@ -181,7 +181,7 @@ gdk_gc_set_tile (gc, NULL); gdk_gc_set_fill (gc, GDK_SOLID); gdk_gc_set_ts_origin (gc, 0, 0); ]]> - The equivalent Cairo code looks like this: + The equivalent cairo code looks like this: - With Cairo, the same effect can be achieved using: + With cairo, the same effect can be achieved using: